(MODULES-1917) Ignore ._ files when building the module tarball
#175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit bumps the version of the module so the we can build a version without ._foo copy files (done by prefixing our `puppet module build` step `COPYFILE_DISABLE=false`).
ajroetker
force-pushed
the
ticket/modules-1917/ignore_osx_build_files_on_module_build
branch
from
139a532
to
ff3b314
Compare
|
@kbarber @ajroetker Seems fine for now, and I imagine we may want to come up with some broader way of making sure we always specify COPYFILE_DISABLE on OS X. |
rbrw
added a commit
that referenced
this pull request
Apr 8, 2015
…_build_files_on_module_build (MODULES-1917) Ignore `._` files when building the module tarball
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version bump to build a version without
._files.